Movable barrier operator configured for remote actuation

ABSTRACT

The present invention is generally a movable barrier operator configured for remote actuation, and more specifically, to a movable barrier operator configured to generate a barrier command in response to an authorized mobile device joining wireless network. The authorization may be established by connecting the mobile device to the operator through a wireless communication means. The wireless communication means may include known protocols such as Bluetooth™, Wi-Fi, NFC, ZigBee™, or any other type of wireless communication.

PRIORITY NOTICE

The present application is a continuation of application Ser. No.14/729,599, filed Jun. 3, 2015, which is a continuation of applicationSer. No. 14/621,250, filed Feb. 12, 2015, which claims Priority fromProvisional Application 62/084,471, filed Nov. 25, 2014, and whichclaims Priority from Provisional Application 62/939,118, filed Feb. 12,2014.

TECHNICAL FIELD OF THE INVENTION

The present invention relates in general to a movable barrier operatorconfigured for remote actuation, and more specifically, to a movablebarrier operator configured to generate a barrier command in response toan authorized mobile device joining a wireless network.

COPYRIGHT AND TRADEMARK NOTICE

A portion of the disclosure of this patent application may containmaterial that is subject to copyright protection. The owner has noobjection to the facsimile reproduction by anyone of the patent documentor the patent disclosure, as it appears in the Patent and TrademarkOffice patent file or records, but otherwise reserves all copyrightswhatsoever.

Certain marks referenced herein may be common law or registeredtrademarks of third parties affiliated or unaffiliated with theapplicant or the assignee. Use of these marks is by way of example andshould not be construed as descriptive or to limit the scope of thisinvention to material associated only with such marks.

BACKGROUND OF THE INVENTION

Typically, access to a secure location, such as a gated area, building,parking structure or walkway, has been controlled remotely by devicesincluding remote controls and the like. Some of these devices include akeypad for inputting a passcode, a radio transmitter, and sometimesother devices that include use of biometric information such as fingerprints, a user's iris, voice or facial characteristics. All of thesedevices require additional expensive equipment, and some of thesedevices require users to carry additional components to access thedesired doorway or gate.

For example, vehicle access to barrier-controlled premises, such as agated community, may require a radio transmitter. These devices do nottypically form an integral part of the vehicle, but rather a separateremote control, which the driver must engage in order to activate asignal that commands the gate to open and grant access to the vehicle.Naturally, these devices may be lost, stolen or misplaced. Newer vehiclemodels offer radio transmitters integral with the vehicle, avoiding theneed to have a separate radio transmitter or remote control.Nevertheless, the user is required to press a button when approachingthe gate or movable barrier that ultimately grants access to thepremises. More importantly, users inviting guests to the premise cannotshare these remote access capabilities, and usually depend on additionalmeans of granting access to their guests.

Similarly, access to secured premises may require access keys. Theseoften prove expensive and may be easily lost or stolen. Furthermore,managing who carries the access key with authorization to enter througha restricted area is exceedingly difficult, as access keys may be sharedor misplaced and used by an unauthorized party.

Therefore, there is a need in the art for a more efficient means ofenabling users with authorized access to a particular premises orlocation, which does not require the user to carry with them keys,remote controls, or require expensive components at each movable barrierin order to gain entry. Furthermore, there is a need to provide a meansof enabling users with access privileges to share or delegate accessprivileges to other users without having to share or provide separatecomponents like keys or remote controls. It is to these ends that thepresent invention has been developed.

BRIEF SUMMARY OF THE INVENTION

To minimize the limitations in the prior art, and to minimize otherlimitations that will be apparent upon reading and understanding thepresent specification, the present invention describes a movable barrieroperator configured for remote actuation from a mobile device. Themovable barrier operator may be configured to generate a barrieractuation command in response to an authorized mobile device joining anexisting common wireless network.

A movable barrier operator system, in accordance with one embodiment ofthe present invention comprises: a mobile device; a movable barrier; alocal wireless network; and a movable barrier operator connected to thelocal wireless network and configured to control the movable barrier,the movable barrier operator including a processor, a memory, and one ormore programs stored in the memory to be executed by the processor, theone or more programs including: instructions for detecting the mobiledevice whenever the mobile device is within a programmable proximity ofthe movable barrier; instructions for broadcasting an invitation for themobile device to join the local wireless network; instructions forreceiving an access request accepting the invitation to join the localwireless network from the mobile device; and instructions for generatinga movable barrier actuation command in response to the mobile devicejoining the local wireless network.

A movable barrier operator system, in accordance with one embodiment ofthe present invention comprises: a movable barrier; a local wirelessnetwork; a server for managing access to the movable barrier, the serverconnected to the local wireless network; and a movable barrier operator,including: a motor configured to control the movable barrier, a networkinterface connecting the movable barrier operator to the local wirelessnetwork, and a controller connected to the network interface and themotor, the controller configured to generate a barrier actuation commandin response to an authorized mobile device joining the local wirelessnetwork.

A movable barrier operator, in accordance with one embodiment of thepresent invention comprises: a wireless network interface forcommunicating with a local wireless network; a motor configured tocontrol a movable barrier; a controller configured to operate the motorand communicate with the wireless network interface, the controllerincluding a processor, a memory, and one or more programs stored in thememory to be executed by the processor, the one or more programsincluding: instructions for detecting a mobile device whenever themobile device is within a programmable proximity of the movable barrier;instructions for broadcasting an invitation for the mobile device tojoin the local wireless network; instructions for receiving an accessrequest accepting the invitation to join the local wireless network fromthe mobile device; and instructions for generating a movable barriercommand in response to the mobile phone joining the local wirelessnetwork.

A system for operating a movable barrier from a vehicle, in accordancewith the present invention, comprises: a vehicle onboard computerincluding a wireless network interface configured to connect to a localwireless network, the vehicle onboard computer including one or moresets of programmable instructions for: detecting an access point to thelocal wireless network, and requesting access to the local wirelessnetwork whenever the vehicle onboard computer is within a programmableproximity to the access point; and a movable barrier operator including:a motor mechanically connected to the movable barrier, and a controllerconfigured to operate the motor and communicate with the local wirelessnetwork, the controller including a processor, a memory, and one or moreprograms stored in the memory to be executed by the processor, the oneor more programs for: broadcasting an invitation to join the localwireless network via the access point; receiving an access request fromthe vehicle onboard computer within a programmable proximity to theaccess point; and generating a movable barrier actuation command inresponse to the vehicle onboard computer joining the local wirelessnetwork.

Another system for operating a movable barrier, in accordance with thepresent invention, comprises: a movable barrier; a local wirelessnetwork; a server for managing access to the movable barrier, the serverconnected to the local wireless network; an access point for providingwireless access to the local wireless network; a movable barrieroperator, including: a motor configured to control the movable barrier,a network interface connecting the movable barrier operator to the localwireless network, and a controller connected to the network interfaceand the motor, the controller configured to generate a barrier actuationcommand in response to an authorized mobile device joining the localwireless network.

A method for remotely controlling a movable barrier, in accordance withthe present invention, comprises: transmitting, from an access point inproximity to the movable barrier, an invitation to join a local wirelessnetwork; receiving, from a mobile device, a request to join the localwireless network, wherein the access request includes authorizationcredentials; providing the mobile device with access to the localwireless network upon verification of the authorization credentials; andautomatically generating a movable barrier command in response to themobile phone joining the local wireless network.

It is an objective of the present invention to provide a movable barrieroperator configured for remote actuation from an onboard computerresiding in a vehicle.

It is another objective of the present invention to provide a movablebarrier operator configured for remote actuation from a smartphone.

It is yet another objective of the present invention to provide a userinterface that facilitates authorization to access a premise.

It is yet another objective of the present invention to eliminate theneed for access keys, remote controls, or other additional components inorder to actuate a movable barrier operator.

These and other advantages and features of the present invention aredescribed herein with specificity so as to make the present inventionunderstandable to one of ordinary skill in the art.

BRIEF DESCRIPTION OF DRAWINGS

Elements in the figures have not necessarily been drawn to scale inorder to enhance their clarity and improve understanding of thesevarious elements and embodiments of the present invention. Furthermore,elements that are known to be common and well understood to those in theindustry may not be depicted in order to provide a clear view of thevarious embodiments of the invention.

FIG. 1 depicts a system in accordance with the present invention.

FIG. 2 depicts a system in accordance with one embodiment of the presentinvention wherein the mobile device comprises a vehicle onboard computerand the operator comprises a gate operator.

FIG. 3 depicts a system in accordance with one embodiment of the presentinvention wherein the mobile device comprises a smartphone and theoperator comprises a locking mechanism.

FIG. 4 is a flowchart depicting one method for remotely actuating amovable barrier in accordance with the present invention.

FIG. 5(a) is a flowchart depicting one method for remotely actuating amovable barrier in accordance with the present invention, wherein theoperator establishes a wireless communication for authorization of amobile device, the operator configured as a wireless access point.

FIG. 5(b) is a flowchart depicting one method for remotely actuating amovable barrier in accordance with the present invention, wherein theoperator establishes a wireless communication for authorization of amobile device, the mobile device configured as a wireless access point.

FIG. 6 is a flowchart depicting one method for remotely actuating amovable barrier in accordance with the present invention, wherein theoperator establishes a wireless communication for authorization of amobile device, and wherein the operator may require a user input priorto generating an actuation command to open the barrier.

FIG. 7 illustrates output of a graphical user interface on a mobiledevice, in accordance with one embodiment of the present invention.

FIG. 8 illustrates output of a graphical user interface on a mobiledevice, in accordance with one embodiment of the present invention.

DESCRIPTION OF THE INVENTION

In the following discussion that addresses a number of embodiments andapplications of the present invention, reference is made to theaccompanying drawings that form a part thereof, where depictions aremade, by way of illustration, of specific embodiments in which theinvention may be practiced. It is to be understood that otherembodiments may be utilized and changes may be made without departingfrom the scope of the invention.

In the following detailed description, a movable barrier operator systemmay be any system that controls a barrier to an entry, an exit, or aview. The barrier could be a door for a small entity (i.e. a person), ora gate for a large entity (i.e. a vehicle), which may swing, slide, rollupwards, lock, unlock, or achieve any other type of action suitable tocontrol access through the barrier. The operator, which controls thebarrier, may move the barrier from an open position to a closed positionand vice-versa, or simply provide a means to lock and unlock thebarrier. The operator may be automatic and may be controlled locally orremotely. Additionally, an operator may comprise one or more motors formoving one or more barriers or a locking mechanism for locking andunlocking one or more doorways. Furthermore, in the present disclosure,the term motor is defined broadly and may be a device that createsmotion, a machine that converts electricity into a mechanical motion, amechanical or electromagnetic device for moving or controlling amechanism or system, and may include without limitation, an electricmotor, an actuator, hydraulics, pneumatics, mechanical locks, or evenelectromagnetic locks. Electromagnetic locks may comprise of a solenoid,magnetic lock or strike, an electromagnet and armature plate, or anyother locking means. Electromagnetic locks may include fail safeelectromagnetic devices that are unlocked when de-energized, or failsecure electromagnetic devices that remain locked when power is lost.

Generally, the present invention involves a movable barrier system,which may include a movable barrier operator configured with a networkinterface to communicate with a mobile device such as a smartphone or anonboard computer of a vehicle. The mobile device may be configured tocommunicate with the operator via a local wireless network, or establisha connection with the local wireless network; the operator may furtherbe configured to receive a signal when the mobile device has joined thelocal wireless network, and generate a movable barrier command thatcontrols the movable barrier. The command to control the barrier may beautomatically generated, or one or more security prompts may berequested of the mobile device via a user interface. The user interfacemay be a graphical user interface (GUI) provided via a smartphoneapplication or an application for vehicle onboard computers. The GUI mayalert the user to input a password, an access key, or a biometric input(e.g. fingerprint) in order to generate the authorization code.Moreover, the system may include a server that hosts the local wirelessnetwork, or a server on a wide area network that can access the movablebarrier operator. The server may include a database and a GUI formanaging the system, or a GUI that allows access to a local database onthe operator. For example, the GUI may allow for authorizations to bedelegated and revoked from the server; new users may be added ordeleted; security levels may be administered for each user; and otherparameters may be altered or otherwise managed remotely. Since eachmobile device must provide the system with an authorization code inorder to join the local wireless network, a system manager may revoke orlimit permissions to mobile devices from the centralized server.

In exemplary embodiments, the operator itself includes a storage modulewith a local database, eliminating the need for a server altogether. Insuch embodiments, the GUI on an authorized mobile device may be used toaccess the database and manage the system. The local wireless networkmay use any number of known technologies such as Wi-Fi™, Bluetooth™ZigBee™, near field communication (NFC), or any other known protocol toestablish a wireless personal area network (WPAN) or any suitablenetwork which may be joined by a mobile device such as a smartphone, atablet, a vehicle onboard computer or any other mobile device usersnormally utilize from day to day. To join the network, the system mayinclude one or more access points, which may use the same or differentprotocol to communicate with the mobile device and facilitate theconnection between the mobile device and the WPAN.

Turning now to the figures, FIG. 1 depicts a system, in accordance withthe present invention, which includes a movable barrier operatorconfigured to generate a barrier command in response to an authorizedmobile device joining an existing wireless network. More specifically,FIG. 1 shows system 100, which includes a movable barrier (barrier 101),a movable barrier operator (operator 102), server 103, a wirelessnetwork such as a WPAN (network 104 a), a wide area network (network 104b), and an access point (AP 105).

Barrier 101 may be any type of barrier as mentioned above. For example,barrier 101 may be a doorway to a walkway, a room, or a storage space;barrier 101 may be a gate to a gated community, a parking structure, orany secured area. In one embodiment, barrier 101 is a sliding gate; inanother embodiment, barrier 101 is a swing gate; in yet anotherembodiment, barrier 101 may be a lockable doorway inside a building or alockable gate on a walkway.

Operator 102 may be any type of movable barrier operator suitable toactuate, operate, or otherwise control access via barrier 101. Thus,operator 102 may be a swing gate operator that swings open, a slidinggate operator that moves a gate on a track, a locking mechanism thatlocks and unlocks a door to an entry, or any other type of operatorsuitable for controlling the type of movable barrier that may beimplemented with system 100. Typically, operator 102 may include networkinterface 106, controller 107, and motor 108.

Operator 102 is configured to communicate with mobile devices 110, 111,and 112 via a network 104 a, which is typically a local wirelesspersonal area network (WPAN) built with known technologies such asZigBee™, Bluetooth™, Wi-Fi™, NFC, or any other suitable protocols forestablishing a short ranged communication between operator 102 andmobile devices 110, 111, 112. In some embodiments, operator 102 is alsoconfigured to communicate with server 103 via a wide area network suchas network 104 b. Network 104 b may be, for example, the World Wide Web.While some applications of the present invention may not require server103, other applications may benefit as server 103 may provide a remotemeans of backing up database 109, or managing system 100 without havingto be in proximity to operator 102.

Server 103 may include one or more computers suitable for connecting tonetwork 104 b and remotely accessing operator 102. Server 103 typicallyincludes a user interface that facilitates management of system 100 aswell as database 109, which holds user information associated withauthorized mobile devices that may be provided access via barrier 101.In some embodiments, database 109 is a back-up database of database 113,which is stored locally at operator 102. In such embodiments, server 103may be accessed by an administrator to manage database 113 from a remotelocation. In yet other embodiments, operator 102 does not include alocal database 113, and system 100 relies solely on a remote database109. In yet other embodiments, server 103 and database 109 are notrequired at all, and operator 102 merely relies on a local database suchas database 113. These various embodiments will be discussed furtherbelow.

Network 104 a is typically a WPAN, as mentioned above, and may implementany number of known technologies. Typically, an access point, such as AP105 may be implemented within a proximity to operator 102. Mobiledevices, such as mobile device 110, 111, and 112, may be detected orotherwise detect AP 105 when within a programmable range. Network 104 athus allows authorized mobile devices to communicate with operator 102.

Network 104 b is typically a wide area network, as mentioned above, forexample the World Wide Web. Network 104 b may be a means to remotelyaccess operator 102 in order to manage system 100 and performmaintenance such as back-up a database, update, and or changepermissions for operator 102.

AP 105 may be any type of access point suitable for connecting mobiledevices 110, 111, and 112 to operator 102 via network 104 a. As such, AP105 may utilize known protocols such as Wi-Fi™, Bluetooth™, ZigBee™,NFC, or any other suitable protocol that enables mobile devices to joinnetwork 104 a.

Network interface 106 may be a wired or wireless network interface; inone embodiment, AP 105 may be a separate component from networkinterface 106; in another embodiment, AP 105 and network interface 106may comprise a single component. Typically however, network interface106 may communicate with AP 105 in order to detect when an authorizeddevice has joined network 104 a. For example, and without limiting thescope of the present invention, in one embodiment, AP 105 may utilize awell known protocol such as Bluetooth™ to detect a mobile device withina predetermined proximity. Once in range, an invitation to join thenetwork 104 a may be provided to the mobile device via AP 105. Thisinvitation may include an authorization protocol or a security protocolin order to verify that the mobile device has permissions to enter orpass through barrier 101. As such, AP 105 may be configured to connectauthorized mobile devices to network 104 a using well known means.Network interface 106 may be configured to alert controller 107 when themobile device has joined the network. In turn, controller 107 maygenerate a desired command for motor 108 to operate barrier 101.

System 100 may use signal strength indication (RSSI) to determine theproximity of the mobile device, and based upon pre-programmedparameters, determine when it is appropriate to provide access viabarrier 101. For example, and without deviating from the scope of thepresent invention, AP 105 and/or network interface 106 may implementRSSI in order to provide users with a programmable means of determininga desirable distance at which a command to control barrier 101 may begenerated by controller 107 of operator 102. This would preventundesirable situations in which an authorized mobile device opens orunlocks a barrier of system 100 unintentionally due to passing withinrange of AP 105.

Controller 107 may comprise of one or more processors configured toaccess and process a set of instructions in a program code stored in aprogrammable memory of operator 102. As such, the one or more processorsof controller 107 may run or execute the one or more set of instructionsstored in the programmable memory in order to perform the variousfunctions of operator 102. For example, controller 107 may processes,relay, or carry out either pre-programmed or user-entered instructionsfor detecting the mobile device whenever the mobile device is within aprogrammable proximity of the movable barrier; instructions forbroadcasting an invitation for the mobile device to join network 104 a;instructions for receiving an access request accepting the invitation tojoin network 104 a from the mobile device; instructions for generating amovable barrier command in response to the mobile device joining network104 a; and any other type of instructions suitable for achieving typicalfunctions of a movable barrier operator. In the present description, amovable barrier command may refer to: an activation of the motor thatmay cause movement of the barrier; an activation of the motor that maycause locking of the barrier; an activation of the motor that may causeunlocking of the barrier; or any other command that achieves a typicalfunction of a movable barrier operator.

Motor 108 may be any motor suitable for controlling a movement orfunction of barrier 101. As such, motor 108 may cause barrier 102 toslide, swing, roll, lock, unlock, or perform the function for whichbarrier 101 has been designed. For example, and without limiting thescope of the present invention, operator 102 may receive a signalindicating that mobile device 110 has joined network 104 a via AP 105.Operator 102 may generate a barrier command in response to this signalin order to unlock barrier 101, which may comprise a doorway. In suchembodiment, motor 108 may be a locking mechanism that locks and unlocksbarrier 101.

Database 109 typically stores user and/or device information associatedwith mobile devices that are authorized to use system 100. Thus,database 109 may be a simple list of user authorization codes,passwords, MAC addresses, or any other information associated with theauthorized mobile devices of system 100, which may be updated by asystem administrator from time to time. To these ends, server 103 mayinclude a software component such as a GUI with access to database 109in order to manage authorized users and client mobile devices.

In one embodiment, as mentioned above, database 109 and server 103 arenot required at all and system 100 relies solely on database 113 tostore a list of authorized users and associated mobile devices. In otherembodiments, database 109 may be a back-up database used to managesystem 100 from a remote location via network 104 b (i.e. the WirelessWorld Wed). In such embodiment, database 109 may be managed andsynchronized with a local database 113. This may allow a user withadministrative permissions to update a list of authorized users, updateuser permissions, or otherwise manage database 113.

Database 113 may be a locally stored database that may be accessed bycontroller 107 of operator 102. As with database 109, database 113typically stores user and/or device information associated with mobiledevices that are authorized to use system 100. Thus, database 113 may bea simple list of unique identifiers associated with one or more mobiledevice, authorization codes, passwords, MAC addresses, or any otherinformation associated with the authorized mobile devices of system 100,which may be updated by a system administrator from time to time.Furthermore, database 113 may include temporary user identificationcodes associated with one or more mobile devices that may be grantedaccess on a temporary basis. Also, database 113 may include a historicaldata or a history of devices that have accessed barrier 101, includingthe dates and times each device has accessed barrier 101. Also, database113 may include profiles for each user or profiles associated with oneor more mobile devices wherein each profile contains user permissionsassociated with a level of access to one or more barriers of system 100.

Database 113 may be managed remotely (i.e. from a computer such asserver 103 via network 104 b), or locally from a mobile device withadministrative privileges. To these ends, a mobile device withadministrative permissions may include a software component such as aGUI with access to database 113 in order to manage authorized users andclient mobile devices.

Mobile devices 110, 111, and 112 may also implement a software componentin order to facilitate implementation of security protocols for system100, including providing each device with permissions to access barrier101. Such software component provides system 100 a means to obtain useror device identification from each mobile device and provides authorizedusers with the right access code, password, or any other means ofauthorization verification to facilitate the user's access via barrier101. The software component may range in complexity: in someembodiments, a simple application for storing an authentication means onthe mobile device 110 may be implemented. An administrator of system 100may provide a user of mobile device 110 with the application, includingthe authentication means. The authentication means may include apassword, access code, a unique identifier, a user identification code,a temporary unique identification code, or any other means ofidentifying and authenticating a mobile device 110. Other more complexapplications may include a GUI that enables the mobile device user withoptions to further more stringent security protocols or have access toadministrative information of system 100.

In one embodiment, more stringent security protocols may be implementedby automatically launching the GUI whenever mobile device 110 enters apredefined range from an access point such as AP 105. The GUI may launcha screen displaying a request to input information to further identifythe user of the mobile device (See FIG. 10, for example).

In another embodiment, access to administrative information of system100 may be provided via mobile device 110 by providing a GUI configuredto display historical data and settings options that allow a user tomanage system 100 parameters (See FIG. 9, for example).

The software component of system 100, whether available at the server,via mobile devices or both, may also include a variety of functions tohelp manage system 100. For example, and without deviating or limitingthe scope of the present invention, a software component may provide thefollowing functions: displaying historical data showing which mobiledevices access barrier 101 and the dates and times that access occurred;issuing a request granting access or generating opening commands (i.e.to unlock or open a barrier) directly from server 103 or mobile device110; locking a particular movable barrier such as a gate, a doorway or awindow; setting system parameter such as timers for locking mechanisms,or timers to maintain a barrier open. For example, a user withadministrative privileges may access select a time during which to keepbarrier 101 opened or accessible to users—this may include a 7-day timerfor unlocking barrier 101 (a doorway) during business hours, a 5-daytimer, for locking and unlocking the doorway during certain days, or anyother timer that helps the system administrator manage access throughbarrier 101.

By implementing the software component with system 100, authorization togain access via barrier 101 may be shared with multiple devices andmanaged at any time. Each device may be individually authorized orde-authorized depending on the administrator's needs without having tore-program a common access code or requiring a user to return an accesskey—as is typically the case with traditional access systems.

Turning to FIG. 2, a system in accordance with one embodiment of thepresent invention is illustrated; in this embodiment, the mobile devicecomprises a vehicle onboard computer and the operator comprises a gateoperator. More specifically, FIG. 2 shows system 200, which includes amovable barrier (barrier 201), a movable barrier operator (operator202), and a vehicle onboard computer (device 205); Operator 202 includesnetwork interface 206, which may be configured to communicate withdevice 205 via a WPAN such as network 204 a, and may also be configuredto communicate with server 203 via network 204 b, which may be a wideaccess network such as the internet. System 200 is very similar tosystem 100, although system 200's designed is focused primarily formovable barrier systems used to control access to vehicles. As such,barrier 201 is typically a gate for controlling vehicle access anddevice 205 is typically a vehicle's onboard computer that has beenconfigured to communicate with operator 202 via network 204 a.

The components of system 200 may be similar to those of system 100. Forexample, operator 202 will similarly include network interface 206,controller 207, and motor 208, which is configured to move barrier 201.Network interface 206 of operator 201 is configured to allow discovery,detection, and connection with device 205.

Device 205 typically includes network interface 209, controller 210, andmemory module 211, which stores executable instructions for providing auser interface—in the illustrated embodiment, the user interfacecomprises GUI 212, which may facilitate more stringent securityprotocols such as requiring a driver to enter an access code prior togenerating a command to move barrier 202.

In this embodiment, the vehicle's onboard computer or device 205, may beconfigured to transmit and receive signals utilizing any number ofprotocols such as Bluetooth™, Wi-Fi™ NFC, ZigBee™ or any other similarcommunication means via network interface 209. As such, networkinterface 209 may be configured with the appropriate protocol to detect,discover, or otherwise establish a communication with network interface206 of operator 202. For example, and without limiting the scope of thepresent invention, as the vehicle approaches barrier 201, the vehicle'sonboard computer may receive an invitation continuously beingbroadcasted from operator 202; alternatively, a discovery mode may beimplemented by device 205 in order to detect network 204 a when within adesired proximity to network interface 206. Once the devices recognizeeach other (i.e. device 205 is authenticated and allowed to join thenetwork or WPAN used by operator 202 to communicate with device 205),operator 202 may generate a barrier command that automatically movesbarrier 201 in order to allow access through.

In other embodiments, an authentication algorithm may be engaged priorto generating a barrier command, wherein the user may be provided with aprompt via GUI 212 to provide authenticating information such as apasscode, a biometric input (e.g. fingerprint on sensor similar to thoseon modern smartphones), or any other input that authorizes operator 202to generate the command to open barrier 201.

In other embodiments, operator 202 may use an RSSI value as mentionedabove in order to avoid undesirable activation of operator 202. In thisway, users can be prompted for passwords, or merely be granted access,only when device 205 enters within a desired proximity to the gate orbarrier 201.

System 200 may include database 215 stored locally at operator 202, thedatabase comprising of authorized user profiles 216 with each userincluding one or more associated mobile devices such as device 205,which have been authorized to access barrier 201. Profiles 216 may beupdated, edited, and shared between one or more locations by accessingserver 203, or in alternative embodiments, where system 200 does notimplement server 203 nor require network 204 b, a mobile device withadministrative permissions may be used to access database 215 and makethe desired adjustments to database 215.

In an embodiment that does not implement server 203, a mobile devicewith administrative permissions may include a smartphone or tableconfigured to communicate with operator 202 via network 204 a and accessdatabase 215 directly. Such mobile device may be used by a fieldtechnician, for example, who may also have access to administrative ormanagement information such as historical data, and other parameters forcontrolling barrier 201.

In the embodiment shown, server 203 is implemented to access operator202 via network 204 a, which may be a local wireless network or a wideaccess network such as the World Wide Web. Server 203 may be useful forgated communities comprising many tenants, and particularly withpremises that include more than one barrier and barrier operators. Withserver 203, each barrier operator may be updated with new users or listof authorized devices that may access the barriers of the premises.Furthermore, as mentioned above, server 203 may be used to store abackup of database 215.

Whether server 203 is implemented, or system 200 need not rely on suchremote access to operator 202, in some embodiments, temporary userauthorizations may be granted so that guests to a location may beprovided with a temporary access. Similarly, any authorized user may beprovided a time limit of authorization via a programmable orpredetermined scheduled length of time, or predetermined expiration datefor authorization. These and other functionalities may be provided to auser via the GUI or user interface. For example, and without limitingthe scope of the present invention, the stored events, such ashistorical access data, or programmed authorizations andde-authorizations, may be provided to a user (e.g. maintenance orsecurity personnel). The GUI may further include means of temporarilyblocking one or more mobile devices associated with vehicles or users ortemporarily granting access to one or more mobile devices associatedwith vehicles or users.

Turning now to the next figure, FIG. 3 depicts a system in accordancewith one embodiment of the present invention wherein the mobile devicecomprises a lockable doorway and the operator is a locking mechanism.More specifically, FIG. 3 shows system 300, including barrier 301,operator 302, mobile device 305, and network interface 306. Althoughsimilar to system 100, system 300 is designed specifically for indoortype of applications wherein the barriers controlled by the systemcomprise of doorways or entries into rooms. Such a system may beimplemented in university settings, hospital premises, office buildings,or any other facility that may require access control to rooms, storage,or any other spaces that may benefit from controlled access by users.

Barrier 301 may be a lockable doorway into an office, a classroom, ahotel room, a hospital room, a storage room, an employees-only room, anequipment room, a medicine cabinet, or any other space within abuilding. Alternatively, barrier 301 may be a gate on a sidewalk orpassage that is located outdoors or indoors, which leads into or out ofa premises.

Operator 302 may include a locking mechanism, such as a magnetic lockingsystem or similar electrical means that causes a locking mechanism toengage and disengage. Whatever the locking mechanism implemented,operator 302 typically includes a network interface 306 forcommunicating with device 305. Network interface 306 may use an RSSIvalue in order to provide users with a programmable means of determininga desirable distance at which a command to control barrier 301 may begenerated by operator 302 once device 305 is detected and authorized.

In this exemplary embodiment, a user of a mobile device that approachesa locked door, retrofitted with an operator in accordance with thepresent invention, may be prompted with a request for a password uponreaching a specific proximity to the locked door. This prompt may bedisplayed on the user's mobile device after the mobile device has beenauthorized and joined network 304.

Device 305 may include a GUI, which has been provided to the mobiledevice via a mobile device application. The mobile device applicationmay be downloaded into device 305 from the internet or from a mobiledevice application server. For example, and without limiting the scopeof the present invention, a mobile application may be provided to device305 via The App Store or any other mobile device host that offersapplications for mobile devices.

Although not shown, a larger system with a server with remote access tooperator 302 may also be implemented with system 300. Such server mayprovide a means to manage database 307, include a back-up database, andprovide administrative management of barrier 302. As explained above, aserver may be useful for implementing a centralized system that allowsan administrator to control more than one barrier. For simplerapplications however, the server may be excluded from system 100 andoperator 302 may be managed by user with administrative permissions. Forexample, and without limiting the scope of the present invention, mobiledevice 305 may include a GUI that enables mobile device 305 to accessdatabase 307 in order to update permissions, etc. Similarly, the GUI indevice 305 may include instructions that facilitate controlling ormodifying programmable instructions stored in a controller of operator302, such as instructions to keep barrier 301 opened, unlocked oraccessible to users during a predetermined period- this may include a7-day timer for unlocking barrier 301 during business hours, a 5-daytimer, for locking and unlocking the doorway during certain days, or anyother timer that helps the system administrator manage access throughbarrier 301.

FIG. 4 is a flowchart depicting one method for remotely actuating amovable barrier in accordance with the present invention, wherein aninvitation is broadcasted via the operator, which may only be acceptedby authorized mobile devices that approach the operator within aprogrammable proximity. More specifically, method 400 is shown in thefollowing steps, however, it is understood that the process may beachieved in any other conceivable sequence without deviating from thescope of the present invention.

In step 401, an invitation to join a local wireless network may betransmitted from an access point, router, or any communications moduleor network interface suitable for connecting a mobile device to a localwireless network. In one embodiment, the operator continuouslybroadcasts the invitation, which only authorized mobile devices mayaccept. The invitation may be transmitted via one or more access pointsusing protocols such as Wi-Fi™, Bluetooth™, ZigBee™, or any other knowntechnology suitable to connect a mobile device to the local wirelessnetwork.

In step 402, an authorized mobile device may send a request to theoperator in order to join the network. In one embodiment, prior tojoining the network, the mobile device must be authenticated. In someembodiments, connecting to the network may require a prompt to the userrequesting authenticating information. In alternative embodiments, ifthe mobile device does not have adequate authenticating information(i.e. the wrong MAC address or other authenticating information) thenthe device will be ignored even if the device detects or discovers theaccess point.

In step 403, an authorized mobile device may provide the authenticatinginformation; for example, the request from the mobile device may includea unique identifier associated with an authorized user. Theauthenticating information may include a MAC address, a passcode orauthorization code provided to the user of the mobile device, orimplemented with a mobile application for the mobile device.

In step 404, the unique identifier of the mobile device may beconfirmed; this may include accessing a database for permissionsassociated with a user profile concerning the mobile device. Where themobile device has the required authorization according to permissionsprovided in the database, in step 405, the mobile device is authorized.If the mobile device does not have the proper authorization, it may beignored or a message may be displayed via the GUI on the mobile deviceinforming the user that access has been denied. If the mobile devicedoes have the proper authorization, the mobile device may be allowedaccess to the local wireless network. In some embodiments, an actuationcommand or barrier command may be generated in step 406; in otherembodiments, a message may be displayed via the GUI of the mobile deviceinforming the user that access has been granted.

In step 406, the operator may be informed that the mobile device hasbeen permitted to join the local wireless network. As such, the operatormay generate a barrier command in order to actuate or initiate controlof the barrier and provide access. The barrier command may comprisemoving the barrier, such as sliding a gate open, or unlocking a doorwaysuch as unlocking a door to a locked office room.

FIG. 5(a) is a flowchart depicting one method for remotely actuating amovable barrier in accordance with the present invention, wherein theoperator establishes a wireless communication for authorization of amobile device, the operator configured as a wireless access point.Method 500 is shown in the following steps, however, it is understoodthat the process may be achieved in any other conceivable sequencewithout deviating from the scope of the present invention.

In step 501 a, an operator may detect a wireless client mobile device.This may be achieved via any number of wireless protocols such as Wi-Fi,Bluetooth™, ZigBee™, or NFC; as such, the mobile device may be a Wi-Ficlient, a Bluetooth™ client, a ZigBee™ client, or an NFC client.

In step 502 a, an authentication protocol may be initiated by thewireless access point in order to authenticate the client device; Instep 503 a the wireless communication via the wireless medium may beestablished if the wireless client device is successfully authenticated;In step 504 a, an access code may be requested via a GUI of the clientdevice; and in step 505 a, a barrier command to actuate a movablebarrier connected to the operator may be generated in order to open,unlock or otherwise control access to through the barrier.

FIG. 5(b) is a flowchart depicting one method for remotely actuating amovable barrier in accordance with the present invention, wherein theoperator establishes a wireless communication for authorization of amobile device, the mobile device configured as a wireless access point.In this embodiment of method 500, similar steps may be practiced,although different device configurations are involved.

In this embodiment, the operator is essentially retrofitted as awireless client device looking to access a wireless access point towhich the operator is allowed to access. Similarly, each authorizedmobile device is configured as a wireless access point adapted to acceptconnection requests by the operator.

In step 501 b the operator will discover a discoverable wireless accesspoint (i.e. authorized mobile device); As with the previous method, thismay be achieved via any number of wireless protocols such as Wi-Fi,Bluetooth™, ZigBee™, or NFC; as such, the operator may be a Wi-Ficlient, a Bluetooth™ client, a ZigBee™ client, or an NFC client.

In step 502 b, the operator may send a request to establishcommunication, the request including an authentication code such as aMAC address, a password, or any other means of authentication. As such,the mobile device may be previously provided with the properauthentication verification information via a mobile application storedin the mobile device; this way, when the operator seeks to join the“access point” the mobile device will have the authenticationinformation necessary to verify and establish communication with theoperator.

In step 503 b, the operator and the mobile device establish wirelesscommunication via the wireless medium. In step 504 a, an access code maybe requested via a GUI of the mobile device; and in step 505 a, abarrier command to actuate a movable barrier connected to the operatormay be generated in order to open, unlock or otherwise control access tothrough the barrier.

FIG. 6 is a flowchart depicting one method for remotely actuating amovable barrier in accordance with the present invention, wherein theoperator establishes a wireless communication for authorization of amobile device, and wherein the operator may require a user input priorto generating an actuation command to open the barrier. Morespecifically, method 600 is shown in the following steps, however, it isunderstood that the process may be achieved in any other conceivablesequence without deviating from the scope of the present invention.

In step 601, the mobile device may be detected. For example, and withoutlimiting the scope of the present invention, this may be achieved bydiscovering a discoverable device, by discovering an access point, bybroadcasting an invitation that may be accepted by authorized devices,or by any other known means of detecting a mobile device via a wirelessnetwork interface in proximity to the mobile device.

In step 602, the mobile device may be authenticated by the networkinterface. In one embodiment, the network interface may include a modulefor initiating a primary security protocol prior to authenticating themobile device and allowing it to join the local wireless network.

In step 603, the mobile device may be authenticated and allowed to jointhe local wireless network. In one embodiment, rather than automaticallygenerating a barrier command, in step 604, a user interface or GUI onthe mobile device may be launched. The GUI may include an outputrequesting an input from the user. This request may require the user toinput a password. In another embodiment, the request may include a voicecommand from the user; the request may include voice recognition toauthorize the user before generating the actuation command; in otherembodiments, the GUI may provide options for the user to eitherphysically (i.e. touch) or verbally (i.e. speech recognition) provide acommand (i.e. open the barrier) before generating a barrier command.

In step 605, the user input may be received from the mobile device. Ofcourse, many other means and options that implement known technologiesmay be employed with the present invention in order to increase securityor improve practicality without deviating from the scope of the presentinvention. After receiving a user input (i.e. a voice command, a touchcommand on a screen of a mobile device, etc.) a barrier command may begenerated to actuate a barrier.

FIG. 7 illustrates output of a graphical user interface on a mobiledevice, in accordance with one embodiment of the present invention. Morespecifically, mobile device 700 is illustrated with display 701 whereinoutput 702 is provided along with tabs 703 and 704. Output 702 may be amessage or instruction for a user infirming the user of a requiredaction or status. As shown output 702 informs the user that access tothrough the desired barrier has been granted. This message may bedisplayed automatically after device 700 is authenticated and joins anetwork triggering the operator to generate a barrier command to allowaccess through the barrier.

Tab 703 may provide a user with a means to glean administrativeinformation such as access history. For example, and without deviatingfrom the scope of the present invention, a user may click or select tab703 in order to see historical data showing which mobile devicesaccessed the barrier in question and the dates and times that accessoccurred.

Tab 704 may provide a user with other type of administrative informationsuch as settings information where a user can glean and controlparameters of the system. For example, and without deviating from thescope of the present invention, a user may be provided with access tosettings such as timers for locking mechanisms, or timers to maintain abarrier open. For example, a user with administrative privileges mayaccess select a time during which to keep a barrier opened or accessibleto users—this may include a 7-day timer for unlocking the barrier duringbusiness hours, a 5-day timer, for locking and unlocking the doorwayduring certain days, or any other timer that helps the systemadministrator manage access through the barrier in question.

FIG. 8 illustrates output of a graphical user interface on a mobiledevice, in accordance with one embodiment of the present invention. Morespecifically, FIG. 8 illustrates output 702 wherein a request forauthenticating information is required and provided to the user of themobile device.

In this embodiment, output 702 may display a message such asinstructions requesting entry of an access code. In alternativeembodiments, the request may be a request to provide biometricinformation such as a fingerprint on sensor 706 of mobile device 700. Asshown, the request for input may include an additional output 705providing a means to enter authentication—in this example, a numericalpasscode to finalize a security protocol and generate a barrier command.

A movable barrier operator with remote monitoring capabilities has beendescribed. The foregoing description of the various exemplaryembodiments of the invention has been presented for the purposes ofillustration and disclosure. It is not intended to be exhaustive or tolimit the invention to the precise form disclosed. Many modificationsand variations are possible in light of the above teaching withoutdeparting from the spirit of the invention.

What is claimed is:
 1. A method performed by an onboard computer on avehicle for controlling a movable barrier, comprising: receiving aninvitation from a movable barrier operator to join a local wirelessnetwork of the movable barrier operator; sending a request to join thelocal wireless network, wherein the request includes a unique identifierassociated with an authorized user; launching an application in responseto receiving the invitation, the application for requesting a user inputassociated with actuation of the movable barrier; and establishingcommunication with the local wireless network.
 2. The method of claim 1,further comprising: sending user credentials to confirm the identity ofthe authorized user to the movable barrier operator.
 3. The method ofclaim 1, wherein the invitation from the movable barrier operatorincludes an instruction to automatically launch the application on theonboard computer.
 4. The method of claim 3, wherein the applicationlaunched by the onboard computer comprises graphical user interface(GUI).
 5. The method of claim 4, wherein the GUI includes an output forrequesting the user input for authenticating the user.
 6. The method ofclaim 5, further comprising: providing via an output of the GUIhistorical data concerning times during which the onboard computer hasaccessed the movable barrier.
 7. A method performed by an onboardcomputer on a vehicle for controlling a movable barrier, comprising:detecting a message inviting the onboard computer on the vehicle to joina local wireless network of a movable barrier operator whenever theonboard computer is within a programmable proximity of the movablebarrier, launching an application, in response to the message,requesting a user input associated with actuation of the movablebarrier; sending an access request in response to receiving the userinput; and joining the local wireless network of the movable barrieroperator.
 8. The method of claim 7, further comprising: determining thedistance of the vehicle to the movable barrier using received signalstrength indication (RSSI).
 9. The method of claim 7, wherein joiningthe local wireless network comprises joining a wireless personal areanetwork (WPAN), and the WPAN utilizes the ZIGBEE protocol, the BLUETOOTHprotocol, Near Field Communication (NFC), or the WI-FI protocol tocommunicate with the movable barrier operator.
 10. A method performed bya movable barrier operator, comprising: transmitting an invitation foran onboard computer on a vehicle to join a local wireless network of themovable barrier operator; receiving a request from the onboard computerto join the local wireless network, wherein the request includes aunique identifier associated with an authorized user; accessing adatabase to match the unique identifier to authenticate the onboardcomputer; authorizing the onboard computer to join the local wirelessnetwork; and generating a movable barrier command in response to theonboard computer joining the local wireless network.
 11. The method ofclaim 10, wherein the invitation to the onboard computer includes aninstruction for the onboard computer to automatically launch anapplication.
 12. The method of claim 10, further comprising: receivingfrom the onboard computer user input comprising user credentials toconfirm the identity of the authorized user.
 13. The method of claim 10,further comprising: sending a request to the onboard computer for userinput comprising user credentials to confirm the identity of theauthorized user; and receiving from the onboard computer the user inputcomprising the user credentials to confirm the identity of theauthorized user.
 14. The method of claim 10, further comprising:determining the distance of the vehicle to the movable barrier usingreceived signal strength indication (RSSI).
 15. The method of claim 10,wherein accessing the database includes: retrieving one or more sets oftemporary user identification codes associated with one or more mobiledevices with a temporary authorization to access the movable barrier.16. The method of claim 10, further comprising: determining whether toallow the onboard computer to join the local wireless network based onuser permissions associated with the unique identifier.
 17. The methodof claim 16, wherein the user permissions include a time designationduring which the onboard computer associated with the unique identifiermay access the movable barrier.
 18. The method of claim 10, furthercomprising: providing a user interface for managing the database. 19.The method of claim 10, further comprising: providing a user interfacefor accessing historical data concerning times during which the onboardcomputer has accessed the movable barrier.
 20. The method of claim 10,further comprising: accessing a server in communication with the movablebarrier operator, the server for managing the database.